home *** CD-ROM | disk | FTP | other *** search
Vim Swap | 1999-09-17 | 16.0 KB | 77 lines |
- b0VIM 4.6
- bagleyd
- liberator
- ~bagleyd/xlock/xlockmore/docs/Revisions
- 3210#"!
- This may or may not work on some versions of Linux, for example
- enabled for linux with the --enable-vtlock option of configure.
- vtlock: xlock now VT lock switch when using -vtlock option. This is
- Thanks to Remi Cohen-Scali/Eric Lassauge <lassauge@sagem.fr> for:
- Thanks to Jouk Jansen and Tom Schmidt for finding -bitmap leaks.
- kumppa leak fixes and starfish leak fixes (one starfish leak remains?)
- Also several fixes for bubble3d on SunOS, now considered stable.
- be a problem? Added verbose fix to color.c stuff.
- Patch for root with no password... not allowed to unlock... could this
- Thanks to Tom Schmidt <tschmidt@micron.com> various fixes and purify report.
- someone else thinks this default should change ... let me know.
- "xlock -display whatever:0" to work as it does in the original. If
- Robert Bihlmeyer <robbe@orcus.priv.at> . I personally would rather
- CUSTOMIZATION part after running configure in config.h . Thanks to
- Allow customization of .Xresources. If using configure uncomment
- kaleid option for qix.
- goop -count now has some effect.
- translation for dclock (accents were not available at the time).
- stripped. Also created a new configure.tcl . Also did the French
- (java, dt stuff) also in xalock and xmlock the #ifdef stuff gets
- This tool (in etc) should help me maintain xlock. Still needs some work.
- Thanks to Charles Vidal <vidalc@club-internet.fr> for his genlauncher.
- removed.
- Now can use g++ on Linux. Working on SunC++. Many stupid warnings
- random mode.
- -fullrandom in 4.11 is confusing so I made it a special option under the
- Also did the dclock Dutch translation.
- On TrueColor it sometimes says it can not get all the colors.
- Major opcode of failed request: 2 (X_ChangedWindowAttributes)
- X Error of failed request: BadMatch (invalid parameter attributes)
- Multiscreen error (seen on Xnest and real multiscreens):
- to use... found unstable on multiscreens and possibly TrueColor.
- and kumppa. starfish must be enabled (using configure --enable-unstable)
- Thanks to Jouk Jansen <joukj@crys.chem.uva.nl> for the port of starfish
- configure fix for group shadow on linux.
- configure fix for afs thanks to Charles Hines <chuck_hines@vnet.ibm.com>.
- Bill Fenner <fenner@parc.xerox.com>.
- should be null. Does not matter for most implementations. Thanks to
- crypt(3) requires strings to be null-terminated. The 3rd character
- BUGS to fix and other stuff to do see docs/TODO.
- from others.
- Adapted from Patrick J. Naughton's original xlock, with lots of help
- Alpha versions may be available through web page or ftp site.
- Please send all bug reports to bagleyd@bigfoot.com .
- be read. If you need help just put "help" in the body.
- If there is trailing signature junk, just put "end" as the last line to
- xlock Xlock/Xlockmore development discussion
- xlock-alpha Xlock alpha ("daily") release announcements
- xlock-beta Xlock beta and production announcements
- ------ -----------------
- choice brief description
- in the body.
- subscribe [choice] [your-email-address]
- Majordomos: Mail to majordomo@tux.org with just
- Maintainer: David A. Bagley <bagleyd@bigfoot.com>
- Web page: http://www.tux.org/~bagleyd/xlockmore.html
- Secondary site: ftp://ftp.x.org/contrib/applications
- Primary site: ftp://ftp.tux.org/pub/tux/bagleyd/xlockmore
- (Help is always appreciated too ;) ).
- If someone has some free time and wants to take over... let me know.
- I have significantly less time to maintain this but I try.
- Adapted from Patrick J. Naughton's original xlock
- xlockmore-4.12 as of 28 September 1998, the maintained version of xlock
- Maintainer: David A. Bagley <bagleyd@bigfoot.com>
- Sun Microsystems Laboratories, Inc. voice: (415) 336 - 1080
- Patrick J. Naughton email: naughton@sun.com
- ______________________________________________________________________
- other special, indirect and consequential damages.
- event will the author be liable for any lost revenue or profits or
- trade secrets or any patents by this file or any part thereof. In no
- shall have no liability with respect to the infringement of copyrights,
-